| Task: Unit Test Assets Design |
| |
 |
| The second activity covers the design of test assets, mainly Test Cases, Test Suites, Test Procedures and Test Scripts, the latter corresponding to unit test automation concerns. |
| Disciplines: Unit Testing |
|
Purpose
Create the test assets in order to evaluate the component code.
|
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
The asset design is responsible for the creation of test cases, test suites, test procedures and test scripts to be
futher used during the execution phase. Information regarding to the previous performed test cycles should be
considered during this phase.
|
Steps
|
Create tests to evaluate the components methods
Based on the previous activity, a test case is generated for each method within the component in order to evaluate
if it works according to the specification. Architecture information should be considered during this step, e.g,
Component Class Diagrams are important, since it helps the tester to verify if the specification conforms with the
component code.
|
Create tests to evaluate the classes integration
After create test cases for each method, the integration among the component's classes can be performed using an
integration strategy, in order to evaluate this integration the test cases are created. The test cases
will evaluate the component's methods based on their specification (e.g. class diagrams), risks performed during
planning step.
|
Verify test coverage
| Verify if the test cases or scripts created are covering the desired path. This step should be performed by
instrumentalizing the code. |
Create test scripts
| Create test scripts to automatic execute the test cases. |
Create test suites
| Group the tests created in the previous step according to a common objective. E.g: Group a set of test or scripts in
order to evaluate a specific feature. |
|
Key Considerations
| The created assets will support execution activities. |
|